Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
大佬能请你帮忙看下是什么原因导致的吗 系统重装很多遍了 硬件也换过不少 蓝屏依然每天一两次,感谢
Loading Dump File [G:\蓝屏分析\050224-25937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`5bc00000 PsLoadedModuleList = 0xfffff807`5c82a790
Debug session time: Thu May 2 16:43:52.959 2024 (UTC + 8:00)
System Uptime: 0 days 7:36:36.281
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`5bffda40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe381`e71b5e20=0000000000000133
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8075c8fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2906
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 60780
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 268467
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8075c8fb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: ffffa60aad06f990 -- (.trap 0xffffa60aad06f990)
Unable to read trap frame at ffffa60a`ad06f990
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: QQScreenshot.exe
STACK_TEXT:
ffffe381`e71b5e18 fffff807`5c034ef4 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`5c8fb320 : nt!KeBugCheckEx
ffffe381`e71b5e20 fffff807`5be4b543 : 00004860`a393a122 ffffe381`e71c0180 00000000`00000000 ffffe381`e71c0180 : nt!KeAccumulateTicks+0x1e7134
ffffe381`e71b5e80 fffff807`5be4b02a : ffffcc85`edf18600 ffffa60a`ad06fa10 00007ffd`4a361500 00000000`0009cc90 : nt!KeClockInterruptNotify+0x453
ffffe381`e71b5f30 fffff807`5bf12d45 : ffffcc85`edf18600 00000000`00000000 00000000`00000000 ffff6a1e`657b1f94 : nt!HalpTimerClockIpiRoutine+0x1a
ffffe381`e71b5f60 fffff807`5bfffa7a : ffffa60a`ad06fa10 ffffcc85`edf18600 00000000`00000859 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffe381`e71b5fb0 fffff807`5c0002a7 : ffff2f95`2f66b4b4 fffff807`5bf268da ffffe381`e71c0180 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffa60a`ad06f990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
SYMBOL_NAME: nt!KeAccumulateTicks+1e7134
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.4291
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1e7134
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
---------